Skip to content

feat(AssetsController): add offhours to token rwa data types - #9792

Merged
satyajeetkolhapure merged 4 commits into
mainfrom
feat/add-offhours-to-token-rwa-data-types
Aug 5, 2026
Merged

feat(AssetsController): add offhours to token rwa data types#9792
satyajeetkolhapure merged 4 commits into
mainfrom
feat/add-offhours-to-token-rwa-data-types

Conversation

@satyajeetkolhapure

@satyajeetkolhapure satyajeetkolhapure commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Explanation

This adds offhours to token rwa data types

Off-hours trading window. Present only when the asset's source reports
off-hours tradability (i.e. tradableSessions contains "offhours").
When absent, off-hours trading is not supported for this asset.
nextOpen: when the off-hours window next opens (ISO-8601)
nextClose: when the off-hours window next closes (ISO-8601)

References

Related to #455

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Additive optional type fields and tests only; no fetch or business-logic changes beyond typing API responses.

Overview
Adds an optional offhours block (nextOpen / nextClose, ISO-8601) to TokenRwaData and RwaTokenData so RWA payloads from the token API can describe off-hours trading windows separately from regular market hours.

fetchRwas behavior is unchanged aside from typing—the new field is passed through when the API includes it and stays absent when off-hours trading is not supported. Tests cover both cases; the changelog documents the shape for consumers.

Reviewed by Cursor Bugbot for commit 5587769. Bugbot is set up for automated code reviews on this repo. Configure here.

Comment thread packages/assets-controllers/CHANGELOG.md Outdated
Comment thread packages/assets-controllers/src/token-service.test.ts
@satyajeetkolhapure
satyajeetkolhapure added this pull request to the merge queue Aug 5, 2026
Merged via the queue into main with commit 2af243d Aug 5, 2026
62 checks passed
@satyajeetkolhapure
satyajeetkolhapure deleted the feat/add-offhours-to-token-rwa-data-types branch August 5, 2026 13:10
@maxime-oe maxime-oe mentioned this pull request Aug 5, 2026
4 tasks
pull Bot pushed a commit to Reality2byte/core that referenced this pull request Aug 5, 2026
## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## [111.1.0]

### Added

- Add `offhours` field to `TokenRwaData` and `RwaTokenData` types to
support off-hours RWA trading windows
([MetaMask#9792](MetaMask#9792))
- `offhours.nextOpen`: ISO-8601 datetime when the next off-hours window
opens
- `offhours.nextClose`: ISO-8601 datetime when the next off-hours window
closes
- Field is only present when the asset's source reports off-hours
tradability; absence means off-hours trading is not supported
- Add 0G (`16661`/`0x4115`) entries in `multicall.ts` and `codefi-v2.ts`
([MetaMask#9760](MetaMask#9760))

### Changed

- Bump `@metamask/account-tree-controller` from `^7.6.0` to `^7.6.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/accounts-controller` from `^39.0.6` to `^39.0.7`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/keyring-controller` from `^27.1.0` to `^27.1.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/multichain-account-service` from `^13.0.0` to
`^13.0.1` ([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/network-enablement-controller` from `^6.0.2` to
`^6.0.3` ([MetaMask#9791](MetaMask#9791))

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and dependency-only changes with no runtime code in this diff;
risk is limited to consumers picking up the new assets-controllers minor
release.
> 
> **Overview**
> **Monorepo release `1180.0.0`** bumps the root
`@metamask/core-monorepo` version and cuts
**`@metamask/assets-controllers` `111.1.0`**, with changelog entries
moved from `[Unreleased]` into the new `111.1.0` section (RWA `offhours`
on `TokenRwaData` / `RwaTokenData`, 0G chain in `multicall.ts` /
`codefi-v2.ts`, plus prior dependency bumps).
> 
> **Downstream packages** now depend on `@metamask/assets-controllers`
**`^111.1.0`** instead of `^111.0.0`: `@metamask/assets-controller`,
`@metamask/bridge-controller`, and
`@metamask/transaction-pay-controller`, with matching changelog notes
and **`yarn.lock`** updates.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
e4fffd7. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants